Azure DevOps Server End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Azure DevOps Server versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Azure DevOps Server is supported, with no end-of-life or end-of-support date announced yet. The next Azure DevOps Server version to reach end of life is TFS 2017, on January 11, 2027. 5 of 15 tracked Azure DevOps Server versions are past end of life; the most recent to reach it, TFS 2015, did so on October 14, 2025. The full Azure DevOps Server lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| TFS 2005 | 2005.SP2 | Jun 17, 2006 | Jul 12, 2016 | 3724 days past EOL | EOL |
| TFS 2010 | 2010.SP1 | Jun 29, 2010 | Jul 14, 2020 | 2261 days past EOL | EOL |
| TFS 2012 | 2012.4 | Oct 31, 2012 | Jan 10, 2023 | 1351 days past EOL | EOL |
| TFS 2013 | 2013.5 | Jan 15, 2014 | Apr 9, 2024 | 896 days past EOL | EOL |
| TFS 2015 | 2015.4.2patch8 | Jul 30, 2015 | Oct 14, 2025 | 343 days past EOL | EOL |
| TFS 2017 | 2017.3.1patch15 | Nov 16, 2016 | Jan 11, 2027 | 111 days remaining | Warning |
| TFS 2018 | 2018.3.2patch20 | Nov 15, 2017 | Jan 11, 2028 | 476 days remaining | Active |
| 2019 | 2019.0.1patch16 | Mar 5, 2019 | Apr 10, 2029 | 931 days remaining | Active |
| 2019 Update 1 | 2019.1.2patch13 | Aug 20, 2019 | Apr 10, 2029 | 931 days remaining | Active |
| 2020 | 2020.0.2patch6 | Aug 25, 2020 | Oct 8, 2030 | 1477 days remaining | Active |
| 2020 Update 1 | 2020.1.2patch19 | May 25, 2021 | Oct 8, 2030 | 1477 days remaining | Active |
| 2022 | 2022.0.1patch5 | Dec 6, 2022 | Jan 11, 2033 | 2303 days remaining | Active |
| 2022 Update 1 | 2022.1patch4 | Nov 28, 2023 | Jan 11, 2033 | 2303 days remaining | Active |
| 2022 Update 2 | 2022.2patch12 | Jul 9, 2024 | Jan 11, 2033 | 2303 days remaining | Active |
| Azure DevOps Server | Patch 8 | Dec 9, 2025 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/azure-devops-server)
Azure DevOps Server release and support pattern
Across the 15 release lines with a published release date, Azure DevOps Server has shipped a new line roughly every 1.3 years (median interval). A line typically stays supported for about 10.1 years from its release to its end-of-life date (measured on the 14 lines with both dates published).
Of the 15 release lines tracked, 5 are past end of life and 10 are still within support. The newest line, continuous, was released December 9, 2025. The next scheduled end of life is 2017 on January 11, 2027 — 111 days from this build. The longest-supported line currently published is 2022.0, to January 11, 2033.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Azure DevOps Server end of life mean for your organization?
When a version of Azure DevOps Server reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Azure DevOps Server should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Azure DevOps Server reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Azure DevOps Server versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Azure DevOps Server has 5 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Azure DevOps Server is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."